home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
EnigmA Amiga Run 1995 October
/
EnigmA AMIGA RUN 01 (1995)(G.R. Edizioni)(IT)[!][issue 1995-10][Aminet 7].iso
/
Aminet
/
comm
/
fido
/
plnc13ex.lha
/
Plutonic.changes
< prev
Wrap
Text File
|
1995-04-30
|
8KB
|
240 lines
==============
Revision Notes
==============
The docs in the main archive are up to date as of version 2.10. This is
included in the archive so you can see the effort that's gone into the
program, and the changes that have been made on the way to the current
release.
This file is in reverse chronological order - ie most recent changes to
the oldest. So to read it from an historical perspective, start at the
bottom and work back up to here!
Version 2.13 (30 Apr 95)
-------------------------
* Changed Display in HEADERLOCK mode slightly, to not clear a screen
when you select NO to the More (Y/n/c)? prompts when messages are being
displayed.
Version 2.12 (28 Apr 95)
-------------------------
* New Keyword (NO)HEADERLOCK. This controls display of messages with
ANSI turned on. Locking the header causes the message header lines to
stay put and the text displayed in the lines beneath this point.
Turning it off gives the OLD display method of simply scrolling the
whole message up the screen.
The keyword controls the initial setting of the HEADERLOCK keyword. It
can also be toggled on and off by using the [A]lter Settings main menu
option once the program is in use. The default is headerlock turned on,
so you don't have to change your config to see this new mode.
* Bugfix: Dangling REPLY kludge in Forwarded messages removed (Thanks
PKN).
Version 2.11 (27 Mar 95)
-------------------------
* New keyword (NO)INTERLACE. Turns on or off interlace screens. The
screenheight will be TWICE that given in the SHEIGHT keyword if you turn
on the interlace mode, so remember that if interlace is on, you should
only specify HALF the number of pixels you really want behind the
SHEIGHT keyword. Naturally, with interlace turned off, the SHEIGHT
gives you exactly that number of pixels (nothing has changed there).
Interlace on a 640*512 screen gives you 60 lines display, virtually all
messages fit on a single screen. Due to the balck background, the
interlace flicker on a 1084 monitor isn't all that bad, and you could
get used to this sort of display. However, having a screen to manage
that's twice the size of the old screen, on an unaccelerated amiga an
interlace screen means Pluto runs noticeably more slowly.
* Touched quotes, where already quoted material NOT commencing with a
space gets a leading space added when put into the quotefile.
For instance, given the text:
XY> Line 1
XY> Line 2
This results in the following appearing in the quote file:
XY> Line 1
XY> Line 2
* Removed an unnecessary prompt.
Version 2.10 (08 Jan 95)
-------------------------
* Same as version 2.09 basically. Publicly released full archive
destined for AmiNet as well as ADS.
Version 2.09 (07 Jan 95)
-------------------------
* Bugfix: Input quotefile for internal editor now doesn't number lines
1,2,2,3,4,5... rather the normal consecutive cardinal numbers
1,2,3,4,5... :-)
* Added the EXWRITTEN keyword, extract from the docs:
---------
EXWRITTEN
---------
This keyword will execute a command (as specified) when a message is
written. I use this to set an environment variable when a message is
written so that after the user logs off the BBS, a full message scan
(rather than just a toss) can be performed resulting in messages users
have written being immediately processed for distribution after they log
off.
Thus my after-BBS mail processing script can go something like:
GETENV MsgWritten
IF $MsgWritten EQ TRUE
TrapToss Toss Scan
Setenv MsgWritten FALSE
ELSE
TrapToss Toss
ENDIF
And then if no messages have been written, a lot of time is saved by not
getting TrapToss to scan all the message areas. This might be useful
for other purposes I can't think of now.
Default:
None. Nothing is executed when a message is written.
Example:
EXWRITTEN Setenv MsgWritten TRUE
Version 2.08 (28 Dec 94)
-------------------------
* There are now completely user-definable Reply, Cross-Reply and
Forward headers instead of the hard coded ones. The defaults are
EXACTLY the same as what Plutonic uses now, however using three new
keywords you can change any or all of these.
The keywords are:
REPLYHEADER
CROSSHEADER
FORWARDHEADER
Behind these keywords you can specify a wide range of embedded percent
commands (and any other characters) which will have the relevant details
substituted in when making up a reply, cross-reply or forwarded message.
For example, the defaults of these keywords are:
REPLYHEADER In a message to %A posted on %d%labout '%s', %W writes:
CROSSHEADER Replying to a msg to %A posted on %d in %l'%p' about '%s',
where %W writes:
(all on one line)
FORWARDHEADER Message forwarded from: %p%l Originally written by: %W%l
Originally written to: %A%l Originally dated: %d %t
(all on one line)
Here is a list of the embedded percent commands currently available
(applicable for all these keywords). Please note that these are CASE
SENSITIVE, and unlike most other keywords, leading and trailing spaces
are NOT stripped.
%% -> a single % sign
%r -> a (hard) carriage return (Ctrl-M) if using your own editor,
otherwise a linefeed (Ctrl-J) if using the internal editor.
Use of a hard carriage return will ensure that the header is not
reflowed. However, it's usually much better to actually re-flow
the header anyway, so I don't recommend the use of this one at
all! (PS: you can also prevent it being reflowed by indenting
the header text at least one space from the left, as exemplified
above in the FORWARDHEADER default)
%l -> a linefeed character (Ctrl-J). This is the one to use 99% of
the time.
For these next two commands, bear in mind the two date formats:
Fido format: 01 Jan 86 02:34:56
Seadog Format: Mon 1 Jan 86 02:34
Since DLG uses the SeaDog format, we see a lot of it in Amiga
message areas.
%d -> Date of original message. I even include the year if we get a
Seadog format date. So with standard Fido format this will be 9
characters long, if the message has Seadog format it's 13
characters long. If this doesn't work properly, the message you
are replying to isn't obeying FTS-1. (IE broken)
%t -> Time of original message. This is always 8 characters long, if
we have a Seadog date format, then :00 is appended to the end of
the time string
%S -> Full subject of the original message
%s -> (Up to) the leftmost 36 characters of the subject of the original
message
%p -> Name of the message area as given in plutonic.areas
%W -> Full name of the writer of the original message
%w -> First name of the writer of the original message
%A -> Full name of the receiver (addressee) of the original message
%a -> First name of the receiver (addressee) of the original message
%M -> if the fromname of the original message is you, yourself (not
case-sensitive) this is translated to the word "me". Otherwise
equivalent to %W
%m -> if the toname of the original message is you, yourself (not
case-sensitive) this is translated to the word "me". Otherwise
equivalent to %A
%I -> if the fromname of the original message is you, yourself (not
case-sensitive) this is translated to the word "I". Otherwise
equivalent to %W
%i -> if the toname of the original message is you, yourself (not
case-sensitive) this is translated to the word "I". Otherwise
equivalent to %A
Unfortunately, since we DON'T KNOW the name of the person you're going
to post the message to until AFTER it's been written, I can't figure out
how to implement a "you" via these embedded percent commands. And
getting the ToName BEFORE the message is written would involve
substantial internal re-structuring, and not something I'm too keen on
doing anyway - I prefer to be asked who to send the message to AFTER
I've written it!
Some examples might be:
ReplyHeader On %d at %t, %W wrote to %m%labout '%s'%l%l Hello %w,%l
CrossHeader In '%p' on %d, %I%lwrote to %m about "%S"
ReplyHeader Hi there, %w, you were talking about%l "%s" on %d:
(etc, etc, etc)